Recent Blog Posts

+ In the hope of streamlining account creation e-mail delivery and mailing list moderations, I have deployed https://en.wikipedia.org/wiki/Sender_Policy_Framework[SPF] and https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail[DKIM] over the weekend for e-mails coming out of `+@jenkins-ci.org+`, which includes account appliations, Confluence, and JIRA. + + + I've also used this opportunity to switch back the sender of JIRA notifications to `+noreply@jenkins-ci.org+`. It was originally this way, then changed to `+jenkinsci-no-reply@googlegroups.com+` when someone complained (on what ground I do not remember any more.) + + + To the degree that I have tested the setup, it is working correctly, but if you notice anything strange, please let me know.

+ As per http://meetings.jenkins-ci.org/jenkins/2012/jenkins.2012-11-14-19.01.log.html#l-68[the discussion in the project meeting today], we created http://lists.jenkins-ci.org/mailman/listinfo/jenkins-events[a new mailing list `+events@lists.jenkins-ci.org+`] for: + + discussing and coordinating Jenkins related events share knowledge between different local communities helping new organizers by having existing community people offering advices improving visibility and transparency of event organization work + + + If you are interested in facilitating local communities (being from Japan, I know for a fact that a local community that speaks the native language makes a big difference in many parts of the world!) + + + The list is http://lists.jenkins-ci.org/mailman/listinfo/jenkins-events[open for anyone to join] and the archive is public. Looking forward to seeing you in the list.

(This was sent as an email to the Hudson dev and users mailing lists after voting concluded, but I thought it’d be good to post it here as well.) The vote is closed, and the results are in. More than half of the total votes were from ineligible voters, but the result would have been the same either way. The final result of all eligible votes is as follows: 214 votes to rename, and 14 for the status quo. You can see the individual votes hudson-jenkins-vote. So what does this mean now? Well, it means Jenkins lives. We’ve registered jenkins-ci.org, though it’s empty at the moment. In the coming days, we will be renaming the existing Google Groups to jenkins-*@googlegroups.com, renaming the Twitter account from @hudsonci to @jenkinsci, and renaming our organization at Github from hudson to jenkinsci. I wanted to make sure everyone had notice ahead of time that this was happening, so that no one gets surprised by changes to their incoming mail, etc. As said before, the initial, interim governance board will consist of me, Kohsuke and, if he and Oracle are willing, Winston. If Winston is unwilling or unable to continue in that role with Jenkins, we will select a replacement interim member. The interim board will work on the details of a more permanent governance process going forward. Discussions on the infrastructure changes (including things like the Maven groupId/artifactIds, etc) will be in public, on these lists. We’re working to get the JIRA and wiki contents migrated over to the Jenkins site, and hope to work with Oracle to get that done in the next couple days. Putting aside logistics, I want to personally thank everyone for voting, and especially thank everyone who voted for renaming for supporting the Jenkins project and its future. Jenkins is not Oracle’s project, nor CloudBee’s project, nor my project, nor Kohsuke’s project - it’s the community’s project, and it’s going to thrive.

As Kohsuke mentioned in this post, the Java.net migration has caught just about everybody off-guard in the Hudson community. The tools we use hosted by Java.net are essentially locked from us until further notice (no ETA on the migration) which is, as you might imagine frustrating both for the core developers but hundreds of plugin developers that make Hudson the best damned CI server on the planet. For source code we’re working on getting something in place for contributions on GitHub thanks to some assistance from the GitHub team. For mailing lists we’ve gone ahead and dumped Java.net mailing lists in favor of a collection of Google Groups: hudson-dev hudson-users hudson-commits hudson-issues Contrary to popular belief, you do not need a Google account to subscribe to these lists, else we wouldn’t have chosen Google Groups. All you need to do is send an email to " hudson-users+subscribe@googlegroups.com" and you’ll receive a confirmation email from the mailing list server shortly. Since our issues.hudson-ci.org isn’t actually hosted on Java.net, but rather on a machine provided by Oracle, they should continue to function as per usual. The login for the systems is somewhat tied to Java.net so I am honestly not sure how stable they will be this week. I apologize sincerely for the confusion and frustration, you can trust that we’re likely ten-times more frustrated with this situation right now. ---

Historically, our fearless leader Kohsuke has blogged on Java.net. The setup made a whole lot of sense when Kohsuke was employed by Sun, then Oracle, which sponsors and runs Java.net. In a post earlier this week discussing console markups, Kohsuke casually pointed out that he will be cross-posting to Java.net, and his personal blog located at kohsuke.org. The first post over on Kohsuke.org welcomes us: For the longest time I haven’t really done anything about kohsuke.org, but as I left Sun/Oracle, I decided to put a bit more effort into it. So this is the new home. For the time being, I plan to post my blogs both on java.net and here. If you’re a reader of feeds, I recommend adding the rss feed for the blog to your list of interesting continuous integration/hacker feeds.

While I work on some screencasts and start to get more"Spotlight" interviews lined up, I figured it’s time for a link roll-up for your Tuesday morning reading. We caught a glimpse of a little Java scoreboard app for Hudson from @davefollett Matt Patterson of Reprocessed.org wrote a great post on continuous integration with Rails with Hudson, running both Rspec and Selenium tests. At the hackathon at Hacker Dojo on Saturday, Kohsuke pointed us all to the Hudson Cafe Press store, where he gets all his Hudson threads. C.J. Adams-Collier seems quite pleased to have builds for IronRuby back online , powered by Hudson. We got a sneak-peak into the first chapter of John Ferguson Smart’s Continuous Integration with Hudson book. Ben Shine showed off some of his UI mock-ups for Hudson.

It’s been quite a busy week, preparing for the Bay Area Hudson hackathon/meetup which starts today, receiving requests for crazy-awesome Hudson stickers and my day job. Regardless, I’ve stumbled across a few links to share in this links roll-up. John Ferguson Smart discusses some of the gotchas with migrating Hudson build jobs from one server to another Learned a bit about how Kim Moir and the Eclipse Foundation are "building better" with Hudson dbaktiar gave a quick overview of installing Hudson on Ubuntu Karma Koala Looking forward even more interesting things to read next week after the hackathon and meetup here in California.

Been a bit pre-occupied this week, so this links roll-up is short and sweet. The JavaDude details a fairly simple test application embedding Glassfish + Netbeans + Hudson Thanks to @chrisbingham, discovered a.NET wrapper for Hudson’s remote API Learned all about getting started with Hudson for .NET projects from Bob Cravens Robert Fletcher wrote a groovy post about testing Grails plugins on Hudson.